home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr09
/
pafab207.zip
/
PAFABLTY.CHG
< prev
next >
Wrap
Text File
|
1993-06-07
|
13KB
|
306 lines
PAFAbility Change History
V2.07 released Feb 1993
Printer codes are now sent at the top of the first and second pages, so
that dot matrix users can turn off the printer to turn the paper over
when using PRINTALT. Since printer settings are lost when the printer
is turned off, the even numbered pages printed with the printer's
default settings instead of the settings needed for the PAFAbility report.
The following problems were corrected:
The combination of pica type and large margins sometimes produced the
following problems: an erroneous message that the FR files might be
corrupted (FRCHK said the files were ok); error initializing dialog box,
status=8301; runtime error #204; unrelated people were included in the
report; the program would hang the system, requiring a reboot; other
unpredicatable results.
If the report included more than 99 generations, the generation
subheaders for 100 on were incorrect. V2.07 will print something like
this - 112 generation - rather than spelling out the number for
generations greater than 99.
V2.06 released Dec 1992
The following problems were corrected:
If the last individual in the PAF database (i.e., the one with the highest
RIN) was in the report, that person was omitted from the index.
A comma is now added after the date of a birth, christening, death, or
burial event when the choice for place preposition is "none". Marriage
was always done this way.
A check for an out of memory condition was added in two places. If this
occurs, the message "Out of memory. Report will be terminated." will
be displayed. The report may not terminate immediately and the message
could occur several times before termination occurs.
V2.05 released Oct 1992
The following problem will not be corrected until version 3:
If the information for the last descendant in a line ended on the last line
of a page, an extra page with only the header and footer is printed before
the next line (in a cascading report) or the index is printed.
The following problems were corrected:
One error message was too long, causing the program to abort with an 8301
status code when it attempted to display the message.
When a child whose line was continued later (a + marked entry) appeared on
the last line on a page, the index entry showed the next higher page number.
People who appeared as a descendant and then subsequently, as a spouse or
descendant, did not have page numbers in the index entry for the subsequent
appearance(s).
Unpredictable results occurred when an individual had more than 30 children.
The program now handles up to 60 children for one individual. If this isn't
enough, please let me know.
If "no index" was selected and the report was aborted, the program either
improperly terminated or hung the system.
If "no index" was selected, sometimes a message appeared saying that there
wasn't room for a 2 column index.
V2.04 released Aug 1992
The following problems were corrected:
If there was not enough memory to add someone to the list of people who's
descendants needed to be printed (i.e., children with +), that person
was inadvertantly dropped from the report.
Program was looking for PAFABLTY.OPT in the current directory only. Now
it will look in the current directory, the directory where PAFABLTY.EXE
is, and all directories in the DOS PATH.
When Help was requested on the Date Options screen via the Help button,
the Help screen was blank.
Page Options/Miscellaneous: When the cursor was on this item and Help
was requested via the F1 key, the help screen was blank.
When nothing is coded in the Sex field, PAF sets the field equal to
an unprintable character. This caused the child sex indicator on the
report to not take up any space and threw off the alignment. PAFAbility
now sets the sex indicator to U if it is not M or F.
V2.03 released 10 Jul 1992
The following problems were corrected:
Compressed print wasn't working on IBM Proprinters.
Show options - paper size selection shown was opposite of what was
selected.
Save options - program aborted if a non-existant directory was specified
Default FR data path was missing the ending backslash which caused the
program to look for the data files one level higher. When the data
files weren't found there, the program said the data path wasn't a PAF
data directory.
V2.02 released 1 Jul 1992
User Interface
Mostly CUA compliant user interface using pull-down menus
and dialog boxes, online help and mouse support
Report can be sent to the printer or written to disk to a
user specified file name
Can be run from any directory. User specifies where PAF data
files reside.
All configuration settings can be saved to/retrieved from a
user specified file name which means that multiple
configurations can be saved and used at will.
User no longer needs to know the RIN of the base individual
for the report. Starting individual can be searched for by
name.
Place name format
Place names are no longer formatted the way PAF does with
commas showing missing levels and no spaces between levels.
Place names are formatted the way one would expect to see
them in a book.
User can choose to have state and country names (in levels 3
and 4) abbreviated.
User can choose to use "in", "at", or no preposition
preceeding place names.
Marriages
The individual's marriages are now numbered. For example:
William Jacob Bennett m. (1) Harriet Latimer ....
The divorce flag is now recognised. For example: William
Jacob Bennett m. (2) Lucy Mattox on 29 Jun 1877 in Van Buren
Co., Iowa; they divorced.
General formatting
Event tags can be abbreviated or spelled out. Born,
christened, died, buried, married or b., chr., d., bur., m.
User can choose pica (10 cpi) or compressed (17 cpi) print.
User selectable margins.
User selectable number of lines to skip after the header,
before the footer and before and after the generation number
subheader.
User can choose whether or not to include the time in the
report header.
User can choose whether or not to eject a page after the
report is printed.
Child's sex is printed next to the number.
User can choose Record System, RIN, or ID field numbering.
Name format
User can choose to include the RIN or ID number with the
name. For example: Earl William Bennett (R-1), b. ....
Date format
All dates now show correctly, i.e., no more "on 1876".
User can choose to omit the preposition (in or on)
preceeding the date. For example, John Bennett, b. 21 Jan
1798.
Index
Title field is no longer included in the index sort.
User can choose a 1 or 2 column index.
User can choose to include birth-death years in the index.
For example: Lester Bennett (1891-1980) 2.
User can choose to include dot leaders in the index entries.
For example:
Lester Bennett (1891-1980) ............. 2
The index sort is now case insensitive.
User can choose to omit the index. This is useful when
creating a one or two page report.
General
User can choose to print only x # of generations on a single
line chart.
User can choose to follow only the direct line ancestors for
the base individual on a cascading report.
The spouse's parents names are shown. For example: William
Jacob Bennett m. (1) Harriett Latimer .... Harriett, dau. of
Samuel Latimer and Nancy Ann Pruitt, b. ....
'They had the following children:' changed to 'Children:'.
The report can be aborted at any time by pressing <ESC>.
Menu item to print the explanation cover sheet. The
compiler's name and address is read from the NAMADD2.DAT
file and printed on the cover sheet.
User can choose whether or not to separate notes with blank
line.
User can choose to show MRIN in marriage data.
In version 1 on the cascading report, end-of-line ancestors
with multiple marriages from whom the base individual was
descended more than once printed more times than they should
have. This has been corrected.
In version 1 on the cascading report, some end-of-line
ancestors were missed and reports weren't printed for them.
This has been corrected.
PAFAbility can now handle the largest database that PAF
allows. There is no limit to the size of the report that can
be created assuming that there is sufficient disk space for
the temporary work files.
Added option to not load the NAME2.DAT file into memory.
XMS support removed since it didn't work.
V1.2 released 7 Oct 1991
XMS support was added to handle the NAME2.DAT file and to
hold the index page being formatted for printing.
The following situations were corrected:
Spelling of "Twelvth" was changed to "Twelfth".
On the cascading report, the progenitor of the second and
subsequent lines had the same person number as the last
person in the previous line.
Unpredictable results occurred when "seenotes" was used in a
date field.
V1.1 released 1 Aug 1991
Bug fix only, no enhancements. The following situations were
corrected:
Occasionally, some event data may not have been printed
and/or event data for one person may have been repeated for
a later person.
In some cases, the child's numbers were not printed. This
occurred when the child had no individual event data, had
marriage data, notes were to be printed and the child had no
notes.
The INDEX.TMP file is now deleted when it is no longer
needed.
In some cases, the individual's name or the marriage data
was repeated after the event data for that person. This only
occurred when notes were to be printed and the individual's
record indicated that there were notes, but there really
weren't any. This condition occurs when the individual had
notes that were deleted via the PAF note editor rather than
through the "delete all notes" option of the FR notes menu.
In the second situation, FR deletes the notes and sets the
note pointer to zero. In the first situation, the notes are
deleted but the note pointer is left pointing to the first
note block.
Some index pages were printed on two pages instead of one,
or a long name may have had garbage printed as the last
character of the page numbers. This only happened when an
index column entry was the maximum size allowed.
If a single line report was requested, and the selected
individual had multiple marriages with no children from the
first marriage, the program went into an infinite loop.
Some people get a message indicating not enough memory for
the index array when there appears to be sufficient memory.
I've changed things around so this shouldn't happen anymore.
Tip: Use the name frequency option to see how many names in your
name file are not being used. If there are a lot, you might
consider using GIE to create a GEDCOM file of your entire
database, then importing the GEDCOM file to a new FR
database. This will eliminate the unused names which means
the smaller name file will use less memory. Another benefit
to doing this is that the NOTES2.DAT file will be
defragmented - each person's notes will be all together,
rather than strung out through the file as they were
entered. This makes retrieval of the notes a little faster.
However, keep in mind that any deleted records in the
INDIV2.DAT and MARR2.DAT files will be eliminated and the
remaining records will have different RINs and MRINs.
Tip: If you store your notes in text files and want them to show
up on your reports, you can clone your database with GEDCOM
to make a temporary database with the notes in the internal
file. The GIE program dated June 1990 or later will include
text file notes in the GEDCOM file.
V1.0 21 June 1991 First release